Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165f4ba5fefbad47b81fb3f3b0012f72e0a070abb83108ddaa99b1d51769f944

Tx prefix hash: 5529939982be015aee00c415402dae841a7d6e978db7b62b0bc23fee6522996e
Tx public key: eaaa730afb63f30db155dbd5273d41b41d2569e83d9cc94a6be0fb4d42c0e289
Timestamp: 1704012396 Timestamp [UCT]: 2023-12-31 08:46:36 Age [y:d:h:m:s]: 01:079:02:45:06
Block: 925002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317672 RingCT/type: yes/0
Extra: 01eaaa730afb63f30db155dbd5273d41b41d2569e83d9cc94a6be0fb4d42c0e28902110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9646fa3d6f7740ca746062f0ffd59739b3d23f0bd2f5322a81cb6170f76fc0b 0.600000000000 1382762 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": 925012, "vin": [ { "gen": { "height": 925002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9646fa3d6f7740ca746062f0ffd59739b3d23f0bd2f5322a81cb6170f76fc0b" } } ], "extra": [ 1, 234, 170, 115, 10, 251, 99, 243, 13, 177, 85, 219, 213, 39, 61, 65, 180, 29, 37, 105, 232, 61, 156, 201, 74, 107, 224, 251, 77, 66, 192, 226, 137, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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