Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 31eb8ee823f352e3c798c149161a5f251c401057607ac19dbf492fe3ef981837

Tx prefix hash: d7eb2022fb5b215a67e8287d1c0fea0a3ffd345318c60901a04335022b653e27
Tx public key: d6e2d9e15a96b5a63a188e16c4286cd8e6ba982fd4bd60912a8677bf5926a8c0
Timestamp: 1750696859 Timestamp [UCT]: 2025-06-23 16:40:59 Age [y:d:h:m:s]: 00:145:06:42:30
Block: 1311256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101731 RingCT/type: yes/0
Extra: 01d6e2d9e15a96b5a63a188e16c4286cd8e6ba982fd4bd60912a8677bf5926a8c0021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6523d2f70d74f4c0e1916301e3cf503abacacfb1fb72ba999a2fa978667e3622 0.600000000000 1798881 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1311266, "vin": [ { "gen": { "height": 1311256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6523d2f70d74f4c0e1916301e3cf503abacacfb1fb72ba999a2fa978667e3622" } } ], "extra": [ 1, 214, 226, 217, 225, 90, 150, 181, 166, 58, 24, 142, 22, 196, 40, 108, 216, 230, 186, 152, 47, 212, 189, 96, 145, 42, 134, 119, 191, 89, 38, 168, 192, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8