Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 181ae81a04421fbbca3cca27832051c28f33566fe0cabe2bd2736ec806e9d652

Tx prefix hash: ba7d64d5881cba08c0cdfffe9ade1bf2b1c19d04511dd418671f3b324485b405
Tx public key: e727bd9e086d222cf89f7412c08a4c4964a79449b7bd96a6ea7d53816c92208b
Timestamp: 1577272734 Timestamp [UCT]: 2019-12-25 11:18:54 Age [y:d:h:m:s]: 05:312:01:55:54
Block: 31355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1370597 RingCT/type: yes/0
Extra: 01e727bd9e086d222cf89f7412c08a4c4964a79449b7bd96a6ea7d53816c92208b0211000000304fb58672000000000000000000

1 output(s) for total of 483.179754951000 dcy

stealth address amount amount idx
00: 54dc295ae5fc7d632bd3402e41a12d89a56ebd4e89ae5d17415555651d5b7837 483.179754951000 51847 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": 31365, "vin": [ { "gen": { "height": 31355 } } ], "vout": [ { "amount": 483179754951, "target": { "key": "54dc295ae5fc7d632bd3402e41a12d89a56ebd4e89ae5d17415555651d5b7837" } } ], "extra": [ 1, 231, 39, 189, 158, 8, 109, 34, 44, 248, 159, 116, 18, 192, 138, 76, 73, 100, 167, 148, 73, 183, 189, 150, 166, 234, 125, 83, 129, 108, 146, 32, 139, 2, 17, 0, 0, 0, 48, 79, 181, 134, 114, 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