Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f547d940dc7c716d072bdb6b35e5b26ea46235a479c6db7006f7a187d5fba15

Tx prefix hash: 81b16153a4097bc38f87a2ca1bd5162b4a1085db329933c4be43a5571ebf3438
Tx public key: a1fabc3d13cf846439fcad1a4e2858d8cadd91b8f58e88f06be1d870d115c7b5
Timestamp: 1704489612 Timestamp [UCT]: 2024-01-05 21:20:12 Age [y:d:h:m:s]: 01:097:01:34:14
Block: 928948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330498 RingCT/type: yes/0
Extra: 01a1fabc3d13cf846439fcad1a4e2858d8cadd91b8f58e88f06be1d870d115c7b502110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e628721f09da93c0c3234baeddb6336c7fc0999a2173f6048a0596b4e657a947 0.600000000000 1386814 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": 928958, "vin": [ { "gen": { "height": 928948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e628721f09da93c0c3234baeddb6336c7fc0999a2173f6048a0596b4e657a947" } } ], "extra": [ 1, 161, 250, 188, 61, 19, 207, 132, 100, 57, 252, 173, 26, 78, 40, 88, 216, 202, 221, 145, 184, 245, 142, 136, 240, 107, 225, 216, 112, 209, 21, 199, 181, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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