Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19900c249d12122829d37378164a5436cdcc3f6a03614878b9fb989986ca06bb

Tx prefix hash: 071312456372a5c9dbbd2276dc15f8544f0aaba3c02e91f1a8f0c0b5e593a171
Tx public key: 3a4edd3eb92c499cd3fbe6a9038df9f74ddbffb5d30fafd3c3c73854cf48f35d
Timestamp: 1745243944 Timestamp [UCT]: 2025-04-21 13:59:04 Age [y:d:h:m:s]: 00:213:05:23:26
Block: 1266331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150110 RingCT/type: yes/0
Extra: 013a4edd3eb92c499cd3fbe6a9038df9f74ddbffb5d30fafd3c3c73854cf48f35d021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcf8d84510bfd8ba937ad634a65111f3f2dd7093baffdba511dc735ab0ff9f26 0.600000000000 1753552 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": 1266341, "vin": [ { "gen": { "height": 1266331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcf8d84510bfd8ba937ad634a65111f3f2dd7093baffdba511dc735ab0ff9f26" } } ], "extra": [ 1, 58, 78, 221, 62, 185, 44, 73, 156, 211, 251, 230, 169, 3, 141, 249, 247, 77, 219, 255, 181, 211, 15, 175, 211, 195, 199, 56, 84, 207, 72, 243, 93, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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