Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb8534b983c32e9d8554d767bf6bf9835c77b96f80e4bc956b1cd273acdd7f26

Tx prefix hash: df174bb30a050e5cab8b9a1864bb0a6fa1ce309186dc9958326c26c549ff04ae
Tx public key: 3f10e90dc87dcea52b8c48cdea01c971a7382b463941839e81b958ba722de70c
Timestamp: 1737474363 Timestamp [UCT]: 2025-01-21 15:46:03 Age [y:d:h:m:s]: 00:149:14:15:53
Block: 1202232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106640 RingCT/type: yes/0
Extra: 013f10e90dc87dcea52b8c48cdea01c971a7382b463941839e81b958ba722de70c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebeb18af55f6e2b1e47c91dcb7e38252daaca4b81117c74d30efa77bfa2222b0 0.600000000000 1688895 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": 1202242, "vin": [ { "gen": { "height": 1202232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebeb18af55f6e2b1e47c91dcb7e38252daaca4b81117c74d30efa77bfa2222b0" } } ], "extra": [ 1, 63, 16, 233, 13, 200, 125, 206, 165, 43, 140, 72, 205, 234, 1, 201, 113, 167, 56, 43, 70, 57, 65, 131, 158, 129, 185, 88, 186, 114, 45, 231, 12, 2, 17, 0, 0, 0, 6, 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