Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5188147b01bffe63ff9aa98af16d93b8f367c8bc112aff40a21c73d533ef5b6

Tx prefix hash: 74bdb979e9f6110aaf407b2764779e33c19587209987dcbd9d4ce060d34e7a98
Tx public key: 424657fe71a945f22d4e47f6ab6fd6cffde1b91641bde8ca70bae59ecff5d6f4
Timestamp: 1738961102 Timestamp [UCT]: 2025-02-07 20:45:02 Age [y:d:h:m:s]: 00:286:06:24:51
Block: 1214321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202341 RingCT/type: yes/0
Extra: 01424657fe71a945f22d4e47f6ab6fd6cffde1b91641bde8ca70bae59ecff5d6f4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 269de38d5e446b57c9edd1d9710ea2d1b36b74244b1b215ce955bd3238eafb54 0.600000000000 1701110 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": 1214331, "vin": [ { "gen": { "height": 1214321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "269de38d5e446b57c9edd1d9710ea2d1b36b74244b1b215ce955bd3238eafb54" } } ], "extra": [ 1, 66, 70, 87, 254, 113, 169, 69, 242, 45, 78, 71, 246, 171, 111, 214, 207, 253, 225, 185, 22, 65, 189, 232, 202, 112, 186, 229, 158, 207, 245, 214, 244, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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