Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 014dc9fc8052d62e99560e522959b4d6a358868400c3f6f90a37ce7f8443d639

Tx prefix hash: 095e16ed3ed1ecbcedb9364bc44c7acb1f33d92fc7c76c240c99bd9ec758d3c9
Tx public key: 7aa1db9e284a93405bbf91666fad37016da9ac1d200bfa47b7719ea11151787a
Timestamp: 1729652884 Timestamp [UCT]: 2024-10-23 03:08:04 Age [y:d:h:m:s]: 00:032:04:18:04
Block: 1137554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22981 RingCT/type: yes/0
Extra: 017aa1db9e284a93405bbf91666fad37016da9ac1d200bfa47b7719ea11151787a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a5836a9bd556798edc9cb262aefdee79e4bb83e257fc7be3a4f0fc7b6f8eecc 0.600000000000 1621067 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": 1137564, "vin": [ { "gen": { "height": 1137554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a5836a9bd556798edc9cb262aefdee79e4bb83e257fc7be3a4f0fc7b6f8eecc" } } ], "extra": [ 1, 122, 161, 219, 158, 40, 74, 147, 64, 91, 191, 145, 102, 111, 173, 55, 1, 109, 169, 172, 29, 32, 11, 250, 71, 183, 113, 158, 161, 17, 81, 120, 122, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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