Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0550b38ac128e212579f1aa613df67d96c57719223af008b7647a1f0bad04118

Tx prefix hash: a087542160d0df2d3f69004a5e6c6e7db30cd464f7edd8deec80a773eb414f16
Tx public key: e4d7774cd1414a42a703d3655a58d2252260e6cae66b9cdab130d425363f2d37
Timestamp: 1759879831 Timestamp [UCT]: 2025-10-07 23:30:31 Age [y:d:h:m:s]: 00:042:01:27:06
Block: 1385054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30131 RingCT/type: yes/0
Extra: 01e4d7774cd1414a42a703d3655a58d2252260e6cae66b9cdab130d425363f2d37021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d619ab731fce241ede2f31d8cc8ecff4ae15d3baed0accb43ccca8bcf4f920 0.600000000000 1873211 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": 1385064, "vin": [ { "gen": { "height": 1385054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d619ab731fce241ede2f31d8cc8ecff4ae15d3baed0accb43ccca8bcf4f920" } } ], "extra": [ 1, 228, 215, 119, 76, 209, 65, 74, 66, 167, 3, 211, 101, 90, 88, 210, 37, 34, 96, 230, 202, 230, 107, 156, 218, 177, 48, 212, 37, 54, 63, 45, 55, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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