Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87975ff30002759aca762691befc8870b01fa4e61730d88b1101ec86bf800689

Tx prefix hash: ff5a5eccdaf32be8a5bfc36f1bc2cfbf4e9ac31caa3be70259a361139017ca3d
Tx public key: b00ee0624b9fbe44d23333899f0f10e0bfd206bc04dc5a5137aba57c7eefc946
Timestamp: 1582369058 Timestamp [UCT]: 2020-02-22 10:57:38 Age [y:d:h:m:s]: 04:258:08:51:28
Block: 70177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077127 RingCT/type: yes/0
Extra: 01b00ee0624b9fbe44d23333899f0f10e0bfd206bc04dc5a5137aba57c7eefc9460211000000074943cd9f000000000000000000

1 output(s) for total of 359.321136193000 dcy

stealth address amount amount idx
00: b4f1b69e32a01ef8c848ea8970b36ba10c41d1b1de073c809d1a52bb09a1afd2 359.321136193000 129555 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": 70187, "vin": [ { "gen": { "height": 70177 } } ], "vout": [ { "amount": 359321136193, "target": { "key": "b4f1b69e32a01ef8c848ea8970b36ba10c41d1b1de073c809d1a52bb09a1afd2" } } ], "extra": [ 1, 176, 14, 224, 98, 75, 159, 190, 68, 210, 51, 51, 137, 159, 15, 16, 224, 191, 210, 6, 188, 4, 220, 90, 81, 55, 171, 165, 124, 126, 239, 201, 70, 2, 17, 0, 0, 0, 7, 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