Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f70c76b4908a2fbe2ac933032f1bda2a74eb665e8cc6e2b6ba650f0035411b

Tx prefix hash: 293989aa5e8cbf74854dfb0840adeaa80da02b203df6b6c452010bd4041b1e00
Tx public key: c246faff21f05e33cdcafed7e58fb1f0a022e29cdec845de2caa774b6c7e1c9a
Timestamp: 1673430019 Timestamp [UCT]: 2023-01-11 09:40:19 Age [y:d:h:m:s]: 02:102:12:26:29
Block: 672329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594949 RingCT/type: yes/0
Extra: 01c246faff21f05e33cdcafed7e58fb1f0a022e29cdec845de2caa774b6c7e1c9a0211000000018b7b6602000000000000000000

1 output(s) for total of 3.633246633000 dcy

stealth address amount amount idx
00: 0bb7466bded9f8ab50f32b397e6980a2127fbfc1a2ec16dd2347eaf671d53421 3.633246633000 1113858 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": 672339, "vin": [ { "gen": { "height": 672329 } } ], "vout": [ { "amount": 3633246633, "target": { "key": "0bb7466bded9f8ab50f32b397e6980a2127fbfc1a2ec16dd2347eaf671d53421" } } ], "extra": [ 1, 194, 70, 250, 255, 33, 240, 94, 51, 205, 202, 254, 215, 229, 143, 177, 240, 160, 34, 226, 156, 222, 200, 69, 222, 44, 170, 119, 75, 108, 126, 28, 154, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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