Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56bf3ba119637e8decab54588a381dc91c2cd09f81318ce8abe301548b004496

Tx prefix hash: 374c60e724090e9b49ad84ab3d89e7614b95fd4a859eaf85bbf83f38e082b580
Tx public key: 2a986d8277f30dc198d0767a9c3bea1a4510d13a7d85d07c4835d123dac4c64f
Timestamp: 1716356718 Timestamp [UCT]: 2024-05-22 05:45:18 Age [y:d:h:m:s]: 00:282:07:48:00
Block: 1027360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201747 RingCT/type: yes/0
Extra: 012a986d8277f30dc198d0767a9c3bea1a4510d13a7d85d07c4835d123dac4c64f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 297d0c0b402528a84427dc0c774824d34ffd9e1566d7e15646942b72e3e95eb4 0.600000000000 1494935 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": 1027370, "vin": [ { "gen": { "height": 1027360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "297d0c0b402528a84427dc0c774824d34ffd9e1566d7e15646942b72e3e95eb4" } } ], "extra": [ 1, 42, 152, 109, 130, 119, 243, 13, 193, 152, 208, 118, 122, 156, 59, 234, 26, 69, 16, 209, 58, 125, 133, 208, 124, 72, 53, 209, 35, 218, 196, 198, 79, 2, 17, 0, 0, 0, 3, 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