Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d8b34f167f72d41bc083e55b461486ba9ea6daf6a48dcf1d12aab6a44a9b3ec

Tx prefix hash: b9b0e8732e04b82d815cdeb4ad004b5b97e5df7c47a6a9c9cebee44e0174e33c
Tx public key: f72280f8b7394709391e5267ba53d59a2adaade6c44b33b90daf517937d5225d
Timestamp: 1723524811 Timestamp [UCT]: 2024-08-13 04:53:31 Age [y:d:h:m:s]: 00:255:12:33:46
Block: 1086774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182520 RingCT/type: yes/0
Extra: 01f72280f8b7394709391e5267ba53d59a2adaade6c44b33b90daf517937d5225d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d5b1ac7bd6fdeee854681d358b77ef9d72e0e4b51386baec3a8815ea6fea4f 0.600000000000 1561373 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": 1086784, "vin": [ { "gen": { "height": 1086774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d5b1ac7bd6fdeee854681d358b77ef9d72e0e4b51386baec3a8815ea6fea4f" } } ], "extra": [ 1, 247, 34, 128, 248, 183, 57, 71, 9, 57, 30, 82, 103, 186, 83, 213, 154, 42, 218, 173, 230, 196, 75, 51, 185, 13, 175, 81, 121, 55, 213, 34, 93, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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