Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca2f58cfe897a3d8926878016e0f7996dfb9d07146f110a76d4620f0ab0ecfd

Tx prefix hash: 53110d93e293a1053d8faa2461375ca54396fb77bc3d8dcd252ef9896241297d
Tx public key: 96c2fa332c2cd770ff5a39325e3f1b2d9ec5ce5c1ae20a36fdd8787bacfee875
Timestamp: 1738270362 Timestamp [UCT]: 2025-01-30 20:52:42 Age [y:d:h:m:s]: 00:136:17:16:07
Block: 1208607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97674 RingCT/type: yes/0
Extra: 0196c2fa332c2cd770ff5a39325e3f1b2d9ec5ce5c1ae20a36fdd8787bacfee875021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6fc9a70266cbb606f2e9d02b3fb3ec9e004a0802e86e2093ded2855b84e8e75 0.600000000000 1695340 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": 1208617, "vin": [ { "gen": { "height": 1208607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6fc9a70266cbb606f2e9d02b3fb3ec9e004a0802e86e2093ded2855b84e8e75" } } ], "extra": [ 1, 150, 194, 250, 51, 44, 44, 215, 112, 255, 90, 57, 50, 94, 63, 27, 45, 158, 197, 206, 92, 26, 226, 10, 54, 253, 216, 120, 123, 172, 254, 232, 117, 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