Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ced3b23637a1147f3c154384d51290fc3f0020dabb0a1f13fa80841ef0517802

Tx prefix hash: aa44ca19ed516cc3915e2628b4ebbcbca61f5a2bff0432cb3d9541ce9593c7c8
Tx public key: 07c2a8cb5e06cfa89c12fb574d8788a309dccc4e48aa385a39920573d7bc7708
Timestamp: 1580780978 Timestamp [UCT]: 2020-02-04 01:49:38 Age [y:d:h:m:s]: 05:030:06:16:03
Block: 57973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173850 RingCT/type: yes/0
Extra: 0107c2a8cb5e06cfa89c12fb574d8788a309dccc4e48aa385a39920573d7bc77080211000000084943cd9f000000000000000000

1 output(s) for total of 394.377569858000 dcy

stealth address amount amount idx
00: 6a3b2c821773ae9e5d5c8aa92e1c0b24073518cc9cdb9d6cff9d88905a6a0414 394.377569858000 107232 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": 57983, "vin": [ { "gen": { "height": 57973 } } ], "vout": [ { "amount": 394377569858, "target": { "key": "6a3b2c821773ae9e5d5c8aa92e1c0b24073518cc9cdb9d6cff9d88905a6a0414" } } ], "extra": [ 1, 7, 194, 168, 203, 94, 6, 207, 168, 156, 18, 251, 87, 77, 135, 136, 163, 9, 220, 204, 78, 72, 170, 56, 90, 57, 146, 5, 115, 215, 188, 119, 8, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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