Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9a286944d0523ff8eb6194b444e32b7f1b9a02f830efd42ac8b1f960ddd48f

Tx prefix hash: f031ce1a4e12d663ae48297ace7708059a71ae8973abf4ff731b31f838557e27
Tx public key: ea68a20a338b42a9d9d954ce54e60908425b8170f209ef8add14979ed3f92123
Timestamp: 1727960453 Timestamp [UCT]: 2024-10-03 13:00:53 Age [y:d:h:m:s]: 00:176:12:43:20
Block: 1123557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125954 RingCT/type: yes/0
Extra: 01ea68a20a338b42a9d9d954ce54e60908425b8170f209ef8add14979ed3f9212302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83eaf1a28b8024ccd79e206c4f2439e3d83e6788facef4cb6c3e6def4c9c542d 0.600000000000 1606092 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": 1123567, "vin": [ { "gen": { "height": 1123557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83eaf1a28b8024ccd79e206c4f2439e3d83e6788facef4cb6c3e6def4c9c542d" } } ], "extra": [ 1, 234, 104, 162, 10, 51, 139, 66, 169, 217, 217, 84, 206, 84, 230, 9, 8, 66, 91, 129, 112, 242, 9, 239, 138, 221, 20, 151, 158, 211, 249, 33, 35, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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