Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977d5025ca201602d722fe09fa1c77822d1900ec5ca743fcadaabe33463934f1

Tx prefix hash: cfd7fb77007011b8321aa02c8c676f87ff5eb2a399ae75d4e4270a5ed8a3f7b9
Tx public key: 6f89c9f2a48d7c30eb74f61fae6bc23782404bef284f7369b30c76c47f23ab36
Timestamp: 1582098817 Timestamp [UCT]: 2020-02-19 07:53:37 Age [y:d:h:m:s]: 04:313:00:58:23
Block: 67945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116239 RingCT/type: yes/0
Extra: 016f89c9f2a48d7c30eb74f61fae6bc23782404bef284f7369b30c76c47f23ab360211000000037adf42d3000000000000000000

1 output(s) for total of 365.486059319000 dcy

stealth address amount amount idx
00: 10214425ba1b1e1ff581bb9a410156c23ffa4efb216cce8c99410964a21f333f 365.486059319000 125171 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": 67955, "vin": [ { "gen": { "height": 67945 } } ], "vout": [ { "amount": 365486059319, "target": { "key": "10214425ba1b1e1ff581bb9a410156c23ffa4efb216cce8c99410964a21f333f" } } ], "extra": [ 1, 111, 137, 201, 242, 164, 141, 124, 48, 235, 116, 246, 31, 174, 107, 194, 55, 130, 64, 75, 239, 40, 79, 115, 105, 179, 12, 118, 196, 127, 35, 171, 54, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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