Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60098ca498da6836c164bbb1dfe4bbc8198ff18782ecbea81642fc8a712054d2

Tx prefix hash: ff2c1b71733b150010a9ce085e6381a07619a9e44b65db7d31603006e273d9fc
Tx public key: 7a72083e980f350526953ecde5117d89d82e8c1830a88c8f1c858eeadc9f3da6
Timestamp: 1732983702 Timestamp [UCT]: 2024-11-30 16:21:42 Age [y:d:h:m:s]: 00:122:14:01:39
Block: 1165103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87396 RingCT/type: yes/0
Extra: 017a72083e980f350526953ecde5117d89d82e8c1830a88c8f1c858eeadc9f3da6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcc723abb80f9d705093f66d2ee87e7e037e073c5b9269c9d94e2c2c892178a4 0.600000000000 1650778 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": 1165113, "vin": [ { "gen": { "height": 1165103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcc723abb80f9d705093f66d2ee87e7e037e073c5b9269c9d94e2c2c892178a4" } } ], "extra": [ 1, 122, 114, 8, 62, 152, 15, 53, 5, 38, 149, 62, 205, 229, 17, 125, 137, 216, 46, 140, 24, 48, 168, 140, 143, 28, 133, 142, 234, 220, 159, 61, 166, 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