Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8953411795bd594fe668582e47fa4c729fc0959631a4d6312504801b6752d3b3

Tx prefix hash: a155a87e8a2d8f9d373582f5ad1705171e2524a676bfcd8fccd6f2f4d116b338
Tx public key: 3b3880f17fe187ea727a9cb2c23f6ccdce7395e1f1c077104f51a0b90a0671dc
Timestamp: 1583080062 Timestamp [UCT]: 2020-03-01 16:27:42 Age [y:d:h:m:s]: 04:338:11:12:24
Block: 74593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135638 RingCT/type: yes/0
Extra: 013b3880f17fe187ea727a9cb2c23f6ccdce7395e1f1c077104f51a0b90a0671dc02110000002612c4732d000000000000000000

1 output(s) for total of 347.410726851000 dcy

stealth address amount amount idx
00: 146bd9b603388956c2a1b890dd3dfa27f76fd743feff5e8e92be6c73a80cf74d 347.410726851000 138013 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": 74603, "vin": [ { "gen": { "height": 74593 } } ], "vout": [ { "amount": 347410726851, "target": { "key": "146bd9b603388956c2a1b890dd3dfa27f76fd743feff5e8e92be6c73a80cf74d" } } ], "extra": [ 1, 59, 56, 128, 241, 127, 225, 135, 234, 114, 122, 156, 178, 194, 63, 108, 205, 206, 115, 149, 225, 241, 192, 119, 16, 79, 81, 160, 185, 10, 6, 113, 220, 2, 17, 0, 0, 0, 38, 18, 196, 115, 45, 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