Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ddc52651d20f6468f4119d3f69d52373b4437f05a555214b3ae159e6ae9ac43

Tx prefix hash: 660e8bd0b4758529d32e3b15652774dc3fd3de518d80d635321f10fb983025ed
Tx public key: e000041e30c38cbf9557b63b0a7670a0ba0729d97eb452d196483cec8fbff1e1
Timestamp: 1649209931 Timestamp [UCT]: 2022-04-06 01:52:11 Age [y:d:h:m:s]: 03:073:19:34:39
Block: 474105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 833102 RingCT/type: yes/0
Extra: 01e000041e30c38cbf9557b63b0a7670a0ba0729d97eb452d196483cec8fbff1e102110000000fd3fcec30000000000000000000

1 output(s) for total of 16.485175239000 dcy

stealth address amount amount idx
00: 375bb39f8309e3b613e91763b75c4718bcc8b5a05b270624098f8f93257fcc9a 16.485175239000 894072 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": 474115, "vin": [ { "gen": { "height": 474105 } } ], "vout": [ { "amount": 16485175239, "target": { "key": "375bb39f8309e3b613e91763b75c4718bcc8b5a05b270624098f8f93257fcc9a" } } ], "extra": [ 1, 224, 0, 4, 30, 48, 195, 140, 191, 149, 87, 182, 59, 10, 118, 112, 160, 186, 7, 41, 217, 126, 180, 82, 209, 150, 72, 60, 236, 143, 191, 241, 225, 2, 17, 0, 0, 0, 15, 211, 252, 236, 48, 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