Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1862ee2873788b162f827683502690ca6dde1f323272db0fd360c7f4d783e8a2

Tx prefix hash: e8cbfd870b06b9c7fc157dcac3b112879b5df3c5a5599ba45372b95a5faf27c3
Tx public key: f40bd713cb1a1bff654cc0a8903542d2002480b7b660c11a01322f0b7e02aae0
Timestamp: 1725744896 Timestamp [UCT]: 2024-09-07 21:34:56 Age [y:d:h:m:s]: 00:123:07:53:06
Block: 1105182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88209 RingCT/type: yes/0
Extra: 01f40bd713cb1a1bff654cc0a8903542d2002480b7b660c11a01322f0b7e02aae0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59f95bc94ea77a1c12b59e0606aa465d6189bbb3140069235b5a4b61fabe2407 0.600000000000 1582521 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": 1105192, "vin": [ { "gen": { "height": 1105182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59f95bc94ea77a1c12b59e0606aa465d6189bbb3140069235b5a4b61fabe2407" } } ], "extra": [ 1, 244, 11, 215, 19, 203, 26, 27, 255, 101, 76, 192, 168, 144, 53, 66, 210, 0, 36, 128, 183, 182, 96, 193, 26, 1, 50, 47, 11, 126, 2, 170, 224, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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