Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3ddd9b2a50ad2d5488d382d21325d3aa4ec8f0e7313c560797818e597044e20

Tx prefix hash: e0bb9b47280f3b3ac3056462f6d6bf706fe930ac02b84d971d6f9e32bb5dc27f
Tx public key: 529e0db3e3e0e479bcd7d73aa170b4e4e5aa7bd9e13e3c9fcee904289da25067
Timestamp: 1745785897 Timestamp [UCT]: 2025-04-27 20:31:37 Age [y:d:h:m:s]: 00:009:04:18:10
Block: 1270823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6559 RingCT/type: yes/0
Extra: 01529e0db3e3e0e479bcd7d73aa170b4e4e5aa7bd9e13e3c9fcee904289da2506702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d509a34dbd6faa944682c072a855cd15a2aa8e15a06bb36416b91774d99482 0.600000000000 1758068 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": 1270833, "vin": [ { "gen": { "height": 1270823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d509a34dbd6faa944682c072a855cd15a2aa8e15a06bb36416b91774d99482" } } ], "extra": [ 1, 82, 158, 13, 179, 227, 224, 228, 121, 188, 215, 215, 58, 161, 112, 180, 228, 229, 170, 123, 217, 225, 62, 60, 159, 206, 233, 4, 40, 157, 162, 80, 103, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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