Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e595d51aecd85dcd7932000a4d0d961d378c76cc38d2ce32b3faa0d2296580

Tx prefix hash: 59bb3d70744ffb6dc8abe7f9368901a7bc9c18f1d1350631d33ddc7cb85aae6f
Tx public key: c0d0f62c8468ee595b33e5b6155c04116711768b8f951117e33e638b1d1fc503
Timestamp: 1588736985 Timestamp [UCT]: 2020-05-06 03:49:45 Age [y:d:h:m:s]: 05:006:18:54:16
Block: 99019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181875 RingCT/type: yes/0
Extra: 01c0d0f62c8468ee595b33e5b6155c04116711768b8f951117e33e638b1d1fc50302110000017160e3cc90000000000000000000

1 output(s) for total of 288.343198476000 dcy

stealth address amount amount idx
00: 55bc077594312a49cb79e5d39a0948b071ae2d01dba203512a036fbeb0471a14 288.343198476000 174853 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": 99029, "vin": [ { "gen": { "height": 99019 } } ], "vout": [ { "amount": 288343198476, "target": { "key": "55bc077594312a49cb79e5d39a0948b071ae2d01dba203512a036fbeb0471a14" } } ], "extra": [ 1, 192, 208, 246, 44, 132, 104, 238, 89, 91, 51, 229, 182, 21, 92, 4, 17, 103, 17, 118, 139, 143, 149, 17, 23, 227, 62, 99, 139, 29, 31, 197, 3, 2, 17, 0, 0, 1, 113, 96, 227, 204, 144, 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