Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af83d34a907dfcf0202921ca5fb203230e32e5246d460233e15ac62f062b9ab1

Tx prefix hash: 57bdfe502a63b217da96e68b824bfec74c722f36bf241e62560401d96b5ecea3
Tx public key: f3ad9d494fa4aa72ffca8385c547aaa4177bce8ed3ed0ab7dc987cc239ccf5a6
Timestamp: 1704574335 Timestamp [UCT]: 2024-01-06 20:52:15 Age [y:d:h:m:s]: 01:306:21:18:34
Block: 929649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478173 RingCT/type: yes/0
Extra: 01f3ad9d494fa4aa72ffca8385c547aaa4177bce8ed3ed0ab7dc987cc239ccf5a602110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2d2e3961a04e7f3455a62f8cdcf35b1b14d4e68f6ce27eafdae21de209b1719 0.600000000000 1387525 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": 929659, "vin": [ { "gen": { "height": 929649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2d2e3961a04e7f3455a62f8cdcf35b1b14d4e68f6ce27eafdae21de209b1719" } } ], "extra": [ 1, 243, 173, 157, 73, 79, 164, 170, 114, 255, 202, 131, 133, 197, 71, 170, 164, 23, 123, 206, 142, 211, 237, 10, 183, 220, 152, 124, 194, 57, 204, 245, 166, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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