Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37e9279afb0f039ebbf7858949e37a13efdcf02b8ed54a9a4d366d9dada7460a

Tx prefix hash: 8e109be942b5e0d020a7976667ec8af9e6be2a862e1060bac2cbed16dc9c555d
Tx public key: 7fdb3dab1f22696b44a52382f2be20b7b4f232f941f61cf10f586c62cfb22204
Timestamp: 1737412441 Timestamp [UCT]: 2025-01-20 22:34:01 Age [y:d:h:m:s]: 00:149:03:38:53
Block: 1201712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106328 RingCT/type: yes/0
Extra: 017fdb3dab1f22696b44a52382f2be20b7b4f232f941f61cf10f586c62cfb22204021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4458dadf946172d7d183f52ae3f024b1f95e7a1a60f9d3aab1bbaf4250cff486 0.600000000000 1688369 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": 1201722, "vin": [ { "gen": { "height": 1201712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4458dadf946172d7d183f52ae3f024b1f95e7a1a60f9d3aab1bbaf4250cff486" } } ], "extra": [ 1, 127, 219, 61, 171, 31, 34, 105, 107, 68, 165, 35, 130, 242, 190, 32, 183, 180, 242, 50, 249, 65, 246, 28, 241, 15, 88, 108, 98, 207, 178, 34, 4, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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