Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a8acd4f21889bd66a9ada1bf23429394b291ae70e44fb327b614f521566552d

Tx prefix hash: a8c4822b37a81ecb4d4c6057ed21ba59b098cbdec70c3eaa16cc4996f8b16fcf
Tx public key: f884356f585e51c1d14097c1f4b4c6a050719f5119728a3337049ce1591ea798
Timestamp: 1712275426 Timestamp [UCT]: 2024-04-05 00:03:46 Age [y:d:h:m:s]: 01:217:15:28:42
Block: 993499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414238 RingCT/type: yes/0
Extra: 01f884356f585e51c1d14097c1f4b4c6a050719f5119728a3337049ce1591ea79802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f22455e8fd8bb9f5dab207a745e73fe821e72c2aceb5786bb179ac9a0534c0d7 0.600000000000 1453885 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": 993509, "vin": [ { "gen": { "height": 993499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f22455e8fd8bb9f5dab207a745e73fe821e72c2aceb5786bb179ac9a0534c0d7" } } ], "extra": [ 1, 248, 132, 53, 111, 88, 94, 81, 193, 209, 64, 151, 193, 244, 180, 198, 160, 80, 113, 159, 81, 25, 114, 138, 51, 55, 4, 156, 225, 89, 30, 167, 152, 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