Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f957aa55cd82e7c2cea5c480c0b2037aeecc20d000cfd55a7f3c6accd1eb7d

Tx prefix hash: bb230108bd6952356339d7c26fb9381627b0ceca624e4d779458d7bdf51ead25
Tx public key: 9ec6f9ab7ef2c292b32d23e5302580f4ddeda20694610733ee1f50cbe45b8615
Timestamp: 1701391116 Timestamp [UCT]: 2023-12-01 00:38:36 Age [y:d:h:m:s]: 01:164:16:27:57
Block: 903279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378884 RingCT/type: yes/0
Extra: 019ec6f9ab7ef2c292b32d23e5302580f4ddeda20694610733ee1f50cbe45b861502110000000433af99f4000000000000000000

1 output(s) for total of 0.623823431000 dcy

stealth address amount amount idx
00: a0acdd353ad6b46c0ae65977182dcec2427c5945185305821f869a922d5364a2 0.623823431000 1359952 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": 903289, "vin": [ { "gen": { "height": 903279 } } ], "vout": [ { "amount": 623823431, "target": { "key": "a0acdd353ad6b46c0ae65977182dcec2427c5945185305821f869a922d5364a2" } } ], "extra": [ 1, 158, 198, 249, 171, 126, 242, 194, 146, 179, 45, 35, 229, 48, 37, 128, 244, 221, 237, 162, 6, 148, 97, 7, 51, 238, 31, 80, 203, 228, 91, 134, 21, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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