Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff181e6aa61d1d16043262313dc31f6dafafb24d13e4182ec7c7d22f3b7c4e1

Tx prefix hash: 782943dfb6b5ba30ba90489963d42af6422c48d3e923b4a4d6dc311536864a0e
Tx public key: abbdcbbb4d36018e8106b4f9725ff4dfaaa4a00b151afe71849df1ebeb654bef
Timestamp: 1638647029 Timestamp [UCT]: 2021-12-04 19:43:49 Age [y:d:h:m:s]: 03:309:08:38:17
Block: 388449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 997479 RingCT/type: yes/0
Extra: 01abbdcbbb4d36018e8106b4f9725ff4dfaaa4a00b151afe71849df1ebeb654bef02110000002e1cab2639000000000000000000

1 output(s) for total of 31.688930243000 dcy

stealth address amount amount idx
00: 4006edb57030d9068527406dcd17e12f4b0be896ad2ea51aa5dfcf2e61e4a538 31.688930243000 783090 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": 388459, "vin": [ { "gen": { "height": 388449 } } ], "vout": [ { "amount": 31688930243, "target": { "key": "4006edb57030d9068527406dcd17e12f4b0be896ad2ea51aa5dfcf2e61e4a538" } } ], "extra": [ 1, 171, 189, 203, 187, 77, 54, 1, 142, 129, 6, 180, 249, 114, 95, 244, 223, 170, 164, 160, 11, 21, 26, 254, 113, 132, 157, 241, 235, 235, 101, 75, 239, 2, 17, 0, 0, 0, 46, 28, 171, 38, 57, 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