Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361e7e5363543a358eafcfee944b507fca0b0705b70b988c4cf9fb9c3c27b149

Tx prefix hash: cd97ca2d8d82735ae7307883b68e28074ca3c6fa3f177fe6a4fcb144066c9b1b
Tx public key: a0a8e1da65c15f5f1c2b8be8f8f48818c3f20d12f6cd2018d1c40700f055df0e
Timestamp: 1632814524 Timestamp [UCT]: 2021-09-28 07:35:24 Age [y:d:h:m:s]: 03:158:04:35:07
Block: 342351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 889593 RingCT/type: yes/0
Extra: 01a0a8e1da65c15f5f1c2b8be8f8f48818c3f20d12f6cd2018d1c40700f055df0e0211000000335d7cc334000000000000000000

1 output(s) for total of 45.047356677000 dcy

stealth address amount amount idx
00: c0bdccfae788f9c76d1757fcf637206275fee964695f24edc414563e297c1178 45.047356677000 703049 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": 342361, "vin": [ { "gen": { "height": 342351 } } ], "vout": [ { "amount": 45047356677, "target": { "key": "c0bdccfae788f9c76d1757fcf637206275fee964695f24edc414563e297c1178" } } ], "extra": [ 1, 160, 168, 225, 218, 101, 193, 95, 95, 28, 43, 139, 232, 248, 244, 136, 24, 195, 242, 13, 18, 246, 205, 32, 24, 209, 196, 7, 0, 240, 85, 223, 14, 2, 17, 0, 0, 0, 51, 93, 124, 195, 52, 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