Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98005cbffea7b72dee20b655a31bcf83a508024b02b0d856a9c74e6a3f98b727

Tx prefix hash: c90f7bd2d4e5ac0debec2b1a35432e07ebf4161a7834db3f1a4c49bf5dce58ed
Tx public key: 9f5682492ecabf286a0d657d7afcd64ee16ce591ea2cea56b2113d642b187e8b
Timestamp: 1729530708 Timestamp [UCT]: 2024-10-21 17:11:48 Age [y:d:h:m:s]: 00:033:20:29:43
Block: 1136527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24195 RingCT/type: yes/0
Extra: 019f5682492ecabf286a0d657d7afcd64ee16ce591ea2cea56b2113d642b187e8b021100000001cab32bb9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7fd38fb12bff7d17256a6f396c19c700ad21d9dfd947048984b03b0264d9fac 0.600000000000 1619872 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": 1136537, "vin": [ { "gen": { "height": 1136527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7fd38fb12bff7d17256a6f396c19c700ad21d9dfd947048984b03b0264d9fac" } } ], "extra": [ 1, 159, 86, 130, 73, 46, 202, 191, 40, 106, 13, 101, 125, 122, 252, 214, 78, 225, 108, 229, 145, 234, 44, 234, 86, 178, 17, 61, 100, 43, 24, 126, 139, 2, 17, 0, 0, 0, 1, 202, 179, 43, 185, 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