Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf354ce5db52e90dde27378601e6d09be2f47556e9269aa2b44d6131056a0eed

Tx prefix hash: d3af74b3ac9789b6c0e8957eee4db345a857f8f56068f5fade94352feaa9b7bc
Tx public key: cf28cea81a46ab73fe47b2cb91e1f2a58b73c81cc2fcec3686c18ce2a814adaa
Timestamp: 1703077692 Timestamp [UCT]: 2023-12-20 13:08:12 Age [y:d:h:m:s]: 01:120:01:27:10
Block: 917265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346940 RingCT/type: yes/0
Extra: 01cf28cea81a46ab73fe47b2cb91e1f2a58b73c81cc2fcec3686c18ce2a814adaa0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34dfe8a72d9c3e1476f0a92a4c5a6897ceaf7e44a566f762061764795f446d0c 0.600000000000 1374835 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": 917275, "vin": [ { "gen": { "height": 917265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34dfe8a72d9c3e1476f0a92a4c5a6897ceaf7e44a566f762061764795f446d0c" } } ], "extra": [ 1, 207, 40, 206, 168, 26, 70, 171, 115, 254, 71, 178, 203, 145, 225, 242, 165, 139, 115, 200, 28, 194, 252, 236, 54, 134, 193, 140, 226, 168, 20, 173, 170, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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