Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e02cdf75d316cf77f66ab0c2477c6802a9768e61062429a303b85d7db3718e

Tx prefix hash: 660b9dec76ed7442405025f37c1b6c5174cf73a9c05d91deb770c9f53cbdf26d
Tx public key: 4152593edb9b64a4b341c4e51c7f9312e0139242e968b7ea503a2b824476c2ea
Timestamp: 1696887713 Timestamp [UCT]: 2023-10-09 21:41:53 Age [y:d:h:m:s]: 01:141:15:09:27
Block: 866146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362237 RingCT/type: yes/0
Extra: 014152593edb9b64a4b341c4e51c7f9312e0139242e968b7ea503a2b824476c2ea021100000001faf35c9c000000000000000000

1 output(s) for total of 0.828130501000 dcy

stealth address amount amount idx
00: 826bd9c581baded3f2f7641474dd609a14601134f5f62c9e941a7b191157219c 0.828130501000 1320718 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": 866156, "vin": [ { "gen": { "height": 866146 } } ], "vout": [ { "amount": 828130501, "target": { "key": "826bd9c581baded3f2f7641474dd609a14601134f5f62c9e941a7b191157219c" } } ], "extra": [ 1, 65, 82, 89, 62, 219, 155, 100, 164, 179, 65, 196, 229, 28, 127, 147, 18, 224, 19, 146, 66, 233, 104, 183, 234, 80, 58, 43, 130, 68, 118, 194, 234, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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