Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0162e84a96ede9b1810b2aa82ac5c0b0145cc60cddc74c1c5d48af04972f30f0

Tx prefix hash: f0851838d27f784cc4bb276cf4f1ab1076ce7c925ffb4d75fce507635c77b1e6
Tx public key: 6e21c49af8b44dfe1c0c95646c15d12863a58b76c848b7258ff63a3b2242f3c3
Timestamp: 1714299198 Timestamp [UCT]: 2024-04-28 10:13:18 Age [y:d:h:m:s]: 00:271:02:38:13
Block: 1010290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194004 RingCT/type: yes/0
Extra: 016e21c49af8b44dfe1c0c95646c15d12863a58b76c848b7258ff63a3b2242f3c302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d77df31567c28cde6ac5fe550d19723c16bbe790c3963387c398245cefcd5dc 0.600000000000 1472200 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": 1010300, "vin": [ { "gen": { "height": 1010290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d77df31567c28cde6ac5fe550d19723c16bbe790c3963387c398245cefcd5dc" } } ], "extra": [ 1, 110, 33, 196, 154, 248, 180, 77, 254, 28, 12, 149, 100, 108, 21, 209, 40, 99, 165, 139, 118, 200, 72, 183, 37, 143, 246, 58, 59, 34, 66, 243, 195, 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