Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fc3a4c9c736ea0fe6a18b7a48fa3bf3080353a9ec12747afd0788ad43f9711

Tx prefix hash: 1a8ddb53df437e9bf3b998dea3a260f120a10b715f1f6aaae8c75b8cf2f79149
Tx public key: a5214aac96f98ef311668429e66ef4e381b82f919dff2f46d7dce35349ca029e
Timestamp: 1701859606 Timestamp [UCT]: 2023-12-06 10:46:46 Age [y:d:h:m:s]: 01:189:02:51:49
Block: 907174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396298 RingCT/type: yes/0
Extra: 01a5214aac96f98ef311668429e66ef4e381b82f919dff2f46d7dce35349ca029e02110000000179bda3be000000000000000000

1 output(s) for total of 0.605558250000 dcy

stealth address amount amount idx
00: 0ea2f983ac0aaf103f7252be8ce5a5523a3ba60dbd22e4da59bec487dcf48469 0.605558250000 1364151 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": 907184, "vin": [ { "gen": { "height": 907174 } } ], "vout": [ { "amount": 605558250, "target": { "key": "0ea2f983ac0aaf103f7252be8ce5a5523a3ba60dbd22e4da59bec487dcf48469" } } ], "extra": [ 1, 165, 33, 74, 172, 150, 249, 142, 243, 17, 102, 132, 41, 230, 110, 244, 227, 129, 184, 47, 145, 157, 255, 47, 70, 215, 220, 227, 83, 73, 202, 2, 158, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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