Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559c34afae2d024c26c819810a40cb1bf8c5dc1fc3b243696714b078796c1622

Tx prefix hash: 89672b15093e563ee6e2b91e6d1d0cc16f8da24f44c4465f14626e8cc3c53f9b
Tx public key: 899dca1c31939adca73019e769c7861a341dd6ca546fa1c8ae0bb0c89ef57197
Timestamp: 1581515619 Timestamp [UCT]: 2020-02-12 13:53:39 Age [y:d:h:m:s]: 04:318:01:34:54
Block: 63497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119461 RingCT/type: yes/0
Extra: 01899dca1c31939adca73019e769c7861a341dd6ca546fa1c8ae0bb0c89ef57197021100000002c71d3ff9000000000000000000

1 output(s) for total of 378.101929259000 dcy

stealth address amount amount idx
00: 1ddf82a7730f732c2d8875c568f698526b1e2c821ac122e84a64fb8dc86eebd5 378.101929259000 117059 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": 63507, "vin": [ { "gen": { "height": 63497 } } ], "vout": [ { "amount": 378101929259, "target": { "key": "1ddf82a7730f732c2d8875c568f698526b1e2c821ac122e84a64fb8dc86eebd5" } } ], "extra": [ 1, 137, 157, 202, 28, 49, 147, 154, 220, 167, 48, 25, 231, 105, 199, 134, 26, 52, 29, 214, 202, 84, 111, 161, 200, 174, 11, 176, 200, 158, 245, 113, 151, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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