Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85222963ee482c00d037b138e0ab63e12bfe3cec1649c16b020ad1791c51c94a

Tx prefix hash: 1a8838cee95274ccf24a7de939c835ef56bcf38728dbb7d0cb46152a562d1907
Tx public key: e93a71239e0470a1ce4716eef0a11f84886ec373a942207b29592cec960fb4c4
Timestamp: 1713439907 Timestamp [UCT]: 2024-04-18 11:31:47 Age [y:d:h:m:s]: 00:363:06:08:57
Block: 1003156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259703 RingCT/type: yes/0
Extra: 01e93a71239e0470a1ce4716eef0a11f84886ec373a942207b29592cec960fb4c402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c1fca58b6e26f7a0021d217e5cc60c407274b948bd77e203aa0f29fb607964a 0.600000000000 1463686 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": 1003166, "vin": [ { "gen": { "height": 1003156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c1fca58b6e26f7a0021d217e5cc60c407274b948bd77e203aa0f29fb607964a" } } ], "extra": [ 1, 233, 58, 113, 35, 158, 4, 112, 161, 206, 71, 22, 238, 240, 161, 31, 132, 136, 110, 195, 115, 169, 66, 32, 123, 41, 89, 44, 236, 150, 15, 180, 196, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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