Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9e4a528d2bac20fd09a09c4b72fe9ffbfe4361e60da723377098b5421b6099f

Tx prefix hash: 2bc9b1893acaa2845bae4d82cec41daadeb3afc2e101ecb7d187a494f2263701
Tx public key: 1f45502198bf0a7241e93370d2666f93c7786d65575e545e29a04ac13e0ef303
Timestamp: 1581243581 Timestamp [UCT]: 2020-02-09 10:19:41 Age [y:d:h:m:s]: 05:269:22:40:10
Block: 61210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343475 RingCT/type: yes/0
Extra: 011f45502198bf0a7241e93370d2666f93c7786d65575e545e29a04ac13e0ef303021100000002724f989b000000000000000000

1 output(s) for total of 384.757130456000 dcy

stealth address amount amount idx
00: 8c8cfeffb43f823b5f5aaadf98c461e6d5419a2488059d92bc4bc056b7cd3caa 384.757130456000 112799 of 0

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": 61220, "vin": [ { "gen": { "height": 61210 } } ], "vout": [ { "amount": 384757130456, "target": { "key": "8c8cfeffb43f823b5f5aaadf98c461e6d5419a2488059d92bc4bc056b7cd3caa" } } ], "extra": [ 1, 31, 69, 80, 33, 152, 191, 10, 114, 65, 233, 51, 112, 210, 102, 111, 147, 199, 120, 109, 101, 87, 94, 84, 94, 41, 160, 74, 193, 62, 14, 243, 3, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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