Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f48ace90355d333888da677426857364b1a1e7a69cd6be399dd1fde5ea227f5

Tx prefix hash: bbb55e259a6a93c99eee21d09718de290b4253a6fff9a5e8b4ca3b458b7a0ab6
Tx public key: 0e94af690fbe9bf05b718cd3733ec875bbbbd3cb9fb5065e2593db9cb1d88028
Timestamp: 1738060424 Timestamp [UCT]: 2025-01-28 10:33:44 Age [y:d:h:m:s]: 00:045:02:04:25
Block: 1206875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32257 RingCT/type: yes/0
Extra: 010e94af690fbe9bf05b718cd3733ec875bbbbd3cb9fb5065e2593db9cb1d88028021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42f92ee82411444d14c020568e71e3c5f16ad63632751ab691406c33159bd75a 0.600000000000 1693588 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": 1206885, "vin": [ { "gen": { "height": 1206875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f92ee82411444d14c020568e71e3c5f16ad63632751ab691406c33159bd75a" } } ], "extra": [ 1, 14, 148, 175, 105, 15, 190, 155, 240, 91, 113, 140, 211, 115, 62, 200, 117, 187, 187, 211, 203, 159, 181, 6, 94, 37, 147, 219, 156, 177, 216, 128, 40, 2, 17, 0, 0, 0, 5, 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