Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fbf4499c0cfc3b75f6ee374ef59e73c335e382bba42d1e4a22a084177fadee2

Tx prefix hash: 175493b77c7f3edd8d2903efebf3281ff23fc5ca540a265457144e970399bc0e
Tx public key: 8f6d9baf3aa1496279ad3d932bd6f9c276d10d5b8074e115d5835e9a9a269819
Timestamp: 1716157850 Timestamp [UCT]: 2024-05-19 22:30:50 Age [y:d:h:m:s]: 01:004:03:14:09
Block: 1025704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263881 RingCT/type: yes/0
Extra: 018f6d9baf3aa1496279ad3d932bd6f9c276d10d5b8074e115d5835e9a9a26981902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a749f9c2c9552a511e4a325ff3bf5db3d410e7d012df26c5fea58066f5b9c44a 0.600000000000 1492387 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": 1025714, "vin": [ { "gen": { "height": 1025704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a749f9c2c9552a511e4a325ff3bf5db3d410e7d012df26c5fea58066f5b9c44a" } } ], "extra": [ 1, 143, 109, 155, 175, 58, 161, 73, 98, 121, 173, 61, 147, 43, 214, 249, 194, 118, 209, 13, 91, 128, 116, 225, 21, 213, 131, 94, 154, 154, 38, 152, 25, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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