Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2026fca2c81bf72869c6d0f50cfacdbfd6437034e35e01246ad7f87c9e3abad

Tx prefix hash: f20d8d2303f06da174ae18a4e3b362b9e12150867d0c77ec30d3cee6748e64f7
Tx public key: 80d9c5069ae98bd150c054d78591f5f1b7fbf22eb8f756282d06dc4cc9851460
Timestamp: 1732636383 Timestamp [UCT]: 2024-11-26 15:53:03 Age [y:d:h:m:s]: 00:118:07:06:51
Block: 1162217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84346 RingCT/type: yes/0
Extra: 0180d9c5069ae98bd150c054d78591f5f1b7fbf22eb8f756282d06dc4cc9851460021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60f265227a4c70d54b24acf2758e19897e03b484d2de1263ea5835eb94d953c 0.600000000000 1647872 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": 1162227, "vin": [ { "gen": { "height": 1162217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60f265227a4c70d54b24acf2758e19897e03b484d2de1263ea5835eb94d953c" } } ], "extra": [ 1, 128, 217, 197, 6, 154, 233, 139, 209, 80, 192, 84, 215, 133, 145, 245, 241, 183, 251, 242, 46, 184, 247, 86, 40, 45, 6, 220, 76, 201, 133, 20, 96, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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