Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20537ed47c62b6a83356d6ef7713bdaf9382b23349b60f76dcae15812b31b969

Tx prefix hash: c8fa59c50683f319416123fa571729d564a7ad6c60c836e90f85984c06a50e58
Tx public key: e95d04919dc9753edb1f992f9ac1d0070f2368f98f47ae854901c0f6c1282178
Timestamp: 1579014784 Timestamp [UCT]: 2020-01-14 15:13:04 Age [y:d:h:m:s]: 05:315:02:39:58
Block: 45379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1373175 RingCT/type: yes/0
Extra: 01e95d04919dc9753edb1f992f9ac1d0070f2368f98f47ae854901c0f6c128217802110000000a4ac5aa02000000000000000000

1 output(s) for total of 434.180879156000 dcy

stealth address amount amount idx
00: 0efefc5d9ed9208774d485a50d1ca870ea6ad7a60ed692fb52cb59e3b1a4fc36 434.180879156000 82889 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": 45389, "vin": [ { "gen": { "height": 45379 } } ], "vout": [ { "amount": 434180879156, "target": { "key": "0efefc5d9ed9208774d485a50d1ca870ea6ad7a60ed692fb52cb59e3b1a4fc36" } } ], "extra": [ 1, 233, 93, 4, 145, 157, 201, 117, 62, 219, 31, 153, 47, 154, 193, 208, 7, 15, 35, 104, 249, 143, 71, 174, 133, 73, 1, 192, 246, 193, 40, 33, 120, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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