Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3263803a67ab6ba50ea3a0d2c468d2fc853841a2852473dd735d51d82f08790c

Tx prefix hash: 3df1cf73e18336769c021f91c7470a510ef5c77dcf4d6cb032e062c079478a15
Tx public key: 4f02f865847c28ca1c339f4c87ece9198a8b6c6910f0405edbe4a9ef936473ad
Timestamp: 1734073689 Timestamp [UCT]: 2024-12-13 07:08:09 Age [y:d:h:m:s]: 00:097:14:57:56
Block: 1174149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69549 RingCT/type: yes/0
Extra: 014f02f865847c28ca1c339f4c87ece9198a8b6c6910f0405edbe4a9ef936473ad021100000001e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6840eec4acf68ac44d830d2dc30a78f29290ef8a3e3213ed5c56fd5903e026d 0.600000000000 1660264 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": 1174159, "vin": [ { "gen": { "height": 1174149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6840eec4acf68ac44d830d2dc30a78f29290ef8a3e3213ed5c56fd5903e026d" } } ], "extra": [ 1, 79, 2, 248, 101, 132, 124, 40, 202, 28, 51, 159, 76, 135, 236, 233, 25, 138, 139, 108, 105, 16, 240, 64, 94, 219, 228, 169, 239, 147, 100, 115, 173, 2, 17, 0, 0, 0, 1, 232, 144, 243, 105, 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