Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eed747f5a7f96898ef60f82ac9331b4d3a2676120aef12ceb7265a89ce9a1c1

Tx prefix hash: e6652c07ec401b6e8628c6926dd4ab693725b25e34108aa690bf23cbce3f5d8a
Tx public key: dd5b758f8ca9812b8028cd23fa6d60602959b3ea7b59cf7564485d854b878444
Timestamp: 1578054562 Timestamp [UCT]: 2020-01-03 12:29:22 Age [y:d:h:m:s]: 05:031:18:18:18
Block: 37712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172604 RingCT/type: yes/0
Extra: 01dd5b758f8ca9812b8028cd23fa6d60602959b3ea7b59cf7564485d854b87844402110000002bdafe52e4000000000000000000

1 output(s) for total of 460.304626501000 dcy

stealth address amount amount idx
00: 60147409e02dec7e17ef49ab01f1f52c0d0c474fe6f5cd9f253ef162a3cb5dce 460.304626501000 64119 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": 37722, "vin": [ { "gen": { "height": 37712 } } ], "vout": [ { "amount": 460304626501, "target": { "key": "60147409e02dec7e17ef49ab01f1f52c0d0c474fe6f5cd9f253ef162a3cb5dce" } } ], "extra": [ 1, 221, 91, 117, 143, 140, 169, 129, 43, 128, 40, 205, 35, 250, 109, 96, 96, 41, 89, 179, 234, 123, 89, 207, 117, 100, 72, 93, 133, 75, 135, 132, 68, 2, 17, 0, 0, 0, 43, 218, 254, 82, 228, 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