Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 268e9843a5e546b202af62c00447f8cdc9cc828eec88e46886e8736e69f5d93c

Tx prefix hash: a7ce51d6dbb20b7ff880f0265845b4af11c709175ffb163fb2dffb1cf5097993
Tx public key: f140ed53fc9424ceb03f6c52ee7ae9603959ba6d6a5f97d49834ea130686fe48
Timestamp: 1681056799 Timestamp [UCT]: 2023-04-09 16:13:19 Age [y:d:h:m:s]: 02:070:02:48:35
Block: 734959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572185 RingCT/type: yes/0
Extra: 01f140ed53fc9424ceb03f6c52ee7ae9603959ba6d6a5f97d49834ea130686fe4802110000000475e3f0e9000000000000000000

1 output(s) for total of 2.253076626000 dcy

stealth address amount amount idx
00: f8ae1da6f06c223f122c328edc6d189b8ec8b25fa728da5b6b01aea8aa5668dc 2.253076626000 1181232 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": 734969, "vin": [ { "gen": { "height": 734959 } } ], "vout": [ { "amount": 2253076626, "target": { "key": "f8ae1da6f06c223f122c328edc6d189b8ec8b25fa728da5b6b01aea8aa5668dc" } } ], "extra": [ 1, 241, 64, 237, 83, 252, 148, 36, 206, 176, 63, 108, 82, 238, 122, 233, 96, 57, 89, 186, 109, 106, 95, 151, 212, 152, 52, 234, 19, 6, 134, 254, 72, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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