Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb97cac9bcccfd1dea804247aec3bf94e68e45d02cb3ca7590dc13648b94dc6

Tx prefix hash: 9ce0ed919b4cf659b79a49f88d322337ebef2df175c58a68a477a87e52fc19a3
Tx public key: 0f49c58e33bcb666152d6af296bdcd4e2da178b703c697e497382bbbe228e323
Timestamp: 1574701774 Timestamp [UCT]: 2019-11-25 17:09:34 Age [y:d:h:m:s]: 05:045:06:41:22
Block: 17290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175211 RingCT/type: yes/0
Extra: 010f49c58e33bcb666152d6af296bdcd4e2da178b703c697e497382bbbe228e323021100000001f95225a5000000000000000000

1 output(s) for total of 538.023687681000 dcy

stealth address amount amount idx
00: 46496af3f83f7519b3eb5fd651a0f3d0c7b7a184165cb7f94602d9aec08deec6 538.023687681000 24931 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": 17300, "vin": [ { "gen": { "height": 17290 } } ], "vout": [ { "amount": 538023687681, "target": { "key": "46496af3f83f7519b3eb5fd651a0f3d0c7b7a184165cb7f94602d9aec08deec6" } } ], "extra": [ 1, 15, 73, 197, 142, 51, 188, 182, 102, 21, 45, 106, 242, 150, 189, 205, 78, 45, 161, 120, 183, 3, 198, 151, 228, 151, 56, 43, 187, 226, 40, 227, 35, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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