Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d4c5b3c45b1a3395d17c11f65b5ae2358cd1decaae0f18e7c8de5e4f0d53671

Tx prefix hash: d350fbe401ee14d33ea9f33564d74a3db9020afbd71df636a5e52f1a8dba97a5
Tx public key: 34e21ecdc9b424c7bb3ccebc4ff8bed99aa6cbcc8cf0be8d8a145721ca694bfb
Timestamp: 1713538310 Timestamp [UCT]: 2024-04-19 14:51:50 Age [y:d:h:m:s]: 01:202:04:40:36
Block: 1003981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403158 RingCT/type: yes/0
Extra: 0134e21ecdc9b424c7bb3ccebc4ff8bed99aa6cbcc8cf0be8d8a145721ca694bfb021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 537cc958dccca490c1f8faf7f0b47ecc8ae8e06524360ea55d2ad67563952716 0.600000000000 1464537 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": 1003991, "vin": [ { "gen": { "height": 1003981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "537cc958dccca490c1f8faf7f0b47ecc8ae8e06524360ea55d2ad67563952716" } } ], "extra": [ 1, 52, 226, 30, 205, 201, 180, 36, 199, 187, 60, 206, 188, 79, 248, 190, 217, 154, 166, 203, 204, 140, 240, 190, 141, 138, 20, 87, 33, 202, 105, 75, 251, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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