Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 952eaf679df9b690262909d717cfd9f718d2e21fdaac66d1027b7a2d40740e68

Tx prefix hash: 8b751b47c10309bd80f428c05fac01088a015fc6ad7c616727f63178cff64590
Tx public key: e506109f4c230ebf07add7e49d263cc3b06ff0c3d80f8e202d3d12b8ab8ed901
Timestamp: 1719174948 Timestamp [UCT]: 2024-06-23 20:35:48 Age [y:d:h:m:s]: 00:359:20:33:49
Block: 1050712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257080 RingCT/type: yes/0
Extra: 01e506109f4c230ebf07add7e49d263cc3b06ff0c3d80f8e202d3d12b8ab8ed90102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38bc53c9a93509066d23bbbbb8bb513acff0a716573c74c112b5c5ef222e3210 0.600000000000 1520887 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": 1050722, "vin": [ { "gen": { "height": 1050712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bc53c9a93509066d23bbbbb8bb513acff0a716573c74c112b5c5ef222e3210" } } ], "extra": [ 1, 229, 6, 16, 159, 76, 35, 14, 191, 7, 173, 215, 228, 157, 38, 60, 195, 176, 111, 240, 195, 216, 15, 142, 32, 45, 61, 18, 184, 171, 142, 217, 1, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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