Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06dbb620f4764db99e30288d8220c6c981dc753cad63db6438df5fa5a70ac17

Tx prefix hash: 5f998074d2a9d82d718c0c43039ea1e4800e10c3fb614618d3c063fa444d1d41
Tx public key: b8f48bacef344916c549e46187d5e5c56016a5dc4c0bc09673f25ed7c0ed9652
Timestamp: 1738444392 Timestamp [UCT]: 2025-02-01 21:13:12 Age [y:d:h:m:s]: 00:292:02:08:49
Block: 1210030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206526 RingCT/type: yes/0
Extra: 01b8f48bacef344916c549e46187d5e5c56016a5dc4c0bc09673f25ed7c0ed9652021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cfed911e651d2eec09f9f68649f12a63c2194bd984aa5787b4af9391463f5d6 0.600000000000 1696777 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": 1210040, "vin": [ { "gen": { "height": 1210030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cfed911e651d2eec09f9f68649f12a63c2194bd984aa5787b4af9391463f5d6" } } ], "extra": [ 1, 184, 244, 139, 172, 239, 52, 73, 22, 197, 73, 228, 97, 135, 213, 229, 197, 96, 22, 165, 220, 76, 11, 192, 150, 115, 242, 94, 215, 192, 237, 150, 82, 2, 17, 0, 0, 0, 4, 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