Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e6a106514440aacc8b54a1fbf1c0dff493c4b73b619d9bd58d73ccab4ca122

Tx prefix hash: 778fc939a5e32ff1237edc932f63ee02898be988ed2d8d70e3aef01e98bebfa3
Tx public key: cddf9e875a0c343046013de28c80fcb9add0ba26a8b729f8249019719580cce4
Timestamp: 1693207169 Timestamp [UCT]: 2023-08-28 07:19:29 Age [y:d:h:m:s]: 01:145:19:38:17
Block: 835599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365531 RingCT/type: yes/0
Extra: 01cddf9e875a0c343046013de28c80fcb9add0ba26a8b729f8249019719580cce4021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.045475156000 dcy

stealth address amount amount idx
00: 3cc5846ea0f273f608b421086cf1a2ed40979cc76d2cc3e9a4eb0550cae0b3fe 1.045475156000 1288153 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": 835609, "vin": [ { "gen": { "height": 835599 } } ], "vout": [ { "amount": 1045475156, "target": { "key": "3cc5846ea0f273f608b421086cf1a2ed40979cc76d2cc3e9a4eb0550cae0b3fe" } } ], "extra": [ 1, 205, 223, 158, 135, 90, 12, 52, 48, 70, 1, 61, 226, 140, 128, 252, 185, 173, 208, 186, 38, 168, 183, 41, 248, 36, 144, 25, 113, 149, 128, 204, 228, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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