Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7904c0ed3e63c0b3e24c717e24a0c7128062fdf3a7ee3979e73a46b2156c912d

Tx prefix hash: 544ce4d69dbc1297ad0af196bd617e1eabb1a699acc17a8401938b312ce9bdf7
Tx public key: b067d878f1491efefd7f8e131c186044f0ffa27766da94d9179de29fa2f83d97
Timestamp: 1700028377 Timestamp [UCT]: 2023-11-15 06:06:17 Age [y:d:h:m:s]: 01:182:22:29:33
Block: 891975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391953 RingCT/type: yes/0
Extra: 01b067d878f1491efefd7f8e131c186044f0ffa27766da94d9179de29fa2f83d9702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.680011948000 dcy

stealth address amount amount idx
00: f7ff604cbdb21c4fe817b14a8b30124e573e928d2590b00ce02a5ab53d764637 0.680011948000 1348032 of 0

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": 891985, "vin": [ { "gen": { "height": 891975 } } ], "vout": [ { "amount": 680011948, "target": { "key": "f7ff604cbdb21c4fe817b14a8b30124e573e928d2590b00ce02a5ab53d764637" } } ], "extra": [ 1, 176, 103, 216, 120, 241, 73, 30, 254, 253, 127, 142, 19, 28, 24, 96, 68, 240, 255, 162, 119, 102, 218, 148, 217, 23, 157, 226, 159, 162, 248, 61, 151, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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