Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824a5010784aa4ee15965ca74aea2efd2f6c61b72e10888e4ff31576fd18c8e5

Tx prefix hash: 9f62c8ef87184bacb1b0474b7032199fe523afcdaf170eb584afe008f19ffe7a
Tx public key: 5b1a8ef9cdb967eb49c9aa570d008d7b117733bffa9b55efd60bce17ecca4526
Timestamp: 1715106331 Timestamp [UCT]: 2024-05-07 18:25:31 Age [y:d:h:m:s]: 00:238:21:25:23
Block: 1016988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170982 RingCT/type: yes/0
Extra: 015b1a8ef9cdb967eb49c9aa570d008d7b117733bffa9b55efd60bce17ecca45260211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67018ea036ea75b75add1d970da19c852c9ec593d65928cb592e39f43708a705 0.600000000000 1480733 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": 1016998, "vin": [ { "gen": { "height": 1016988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67018ea036ea75b75add1d970da19c852c9ec593d65928cb592e39f43708a705" } } ], "extra": [ 1, 91, 26, 142, 249, 205, 185, 103, 235, 73, 201, 170, 87, 13, 0, 141, 123, 17, 119, 51, 191, 250, 155, 85, 239, 214, 11, 206, 23, 236, 202, 69, 38, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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