Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30097d1fb160054dc07bfe4cdd561ab69e37eac0c5757e6f81cc40456000dc0c

Tx prefix hash: d6dd8a76eeb058c6f98e25e1acb986cbcb5d5fa1fe2eb05fbd0cea4b89caa7fd
Tx public key: 417236226e0fe748d4e91d741c402fae9ea2e1bb7cfd4028628c514358eae946
Timestamp: 1713924424 Timestamp [UCT]: 2024-04-24 02:07:04 Age [y:d:h:m:s]: 01:028:12:59:05
Block: 1007188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281360 RingCT/type: yes/0
Extra: 01417236226e0fe748d4e91d741c402fae9ea2e1bb7cfd4028628c514358eae94602110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c425ea97644150f13f94c635afbfe37f6bb3d97ab45cbaec0be79b198dcfd76b 0.600000000000 1468446 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": 1007198, "vin": [ { "gen": { "height": 1007188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c425ea97644150f13f94c635afbfe37f6bb3d97ab45cbaec0be79b198dcfd76b" } } ], "extra": [ 1, 65, 114, 54, 34, 110, 15, 231, 72, 212, 233, 29, 116, 28, 64, 47, 174, 158, 162, 225, 187, 124, 253, 64, 40, 98, 140, 81, 67, 88, 234, 233, 70, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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