Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d877e5009197f4adc1ae4ea02aef57fcf8c647768560fb7ee33e0023249b3c

Tx prefix hash: 9017b72c67ed12bb2a7ab808d7c6aba048b5a60fa450cb6ec6fcadba20b95e88
Tx public key: 8f315d1666c4fdc01bdfb3a37aeffab7386cccc8de05eaa928c586b01949ce4e
Timestamp: 1713396552 Timestamp [UCT]: 2024-04-17 23:29:12 Age [y:d:h:m:s]: 00:220:06:07:43
Block: 1002792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157687 RingCT/type: yes/0
Extra: 018f315d1666c4fdc01bdfb3a37aeffab7386cccc8de05eaa928c586b01949ce4e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb54fcf7c4d54936e5bde8c76a262ba25bdc10f8495af7c03c5298ee529ef41 0.600000000000 1463316 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": 1002802, "vin": [ { "gen": { "height": 1002792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb54fcf7c4d54936e5bde8c76a262ba25bdc10f8495af7c03c5298ee529ef41" } } ], "extra": [ 1, 143, 49, 93, 22, 102, 196, 253, 192, 27, 223, 179, 163, 122, 239, 250, 183, 56, 108, 204, 200, 222, 5, 234, 169, 40, 197, 134, 176, 25, 73, 206, 78, 2, 17, 0, 0, 0, 2, 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