Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ce1f33326715300f769c2896bb245fe6a5725319ffaa853371e08fd1868b10

Tx prefix hash: d405ae5642527244b99e046fb92c3b2ce9d8e4c251673ded5dbec1051651c4ea
Tx public key: 794103cbb5cb7020a9141bcd0cf938638df1e2d8faa11cd4bd13c9b998089b35
Timestamp: 1578652111 Timestamp [UCT]: 2020-01-10 10:28:31 Age [y:d:h:m:s]: 05:051:10:55:32
Block: 42506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186838 RingCT/type: yes/0
Extra: 01794103cbb5cb7020a9141bcd0cf938638df1e2d8faa11cd4bd13c9b998089b350211000000104ac5aa02000000000000000000

1 output(s) for total of 443.772944301000 dcy

stealth address amount amount idx
00: ab211cff7df424295f957b06fb6e6784faa16d4c69ce63a25a81b26ff195d0de 443.772944301000 76627 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": 42516, "vin": [ { "gen": { "height": 42506 } } ], "vout": [ { "amount": 443772944301, "target": { "key": "ab211cff7df424295f957b06fb6e6784faa16d4c69ce63a25a81b26ff195d0de" } } ], "extra": [ 1, 121, 65, 3, 203, 181, 203, 112, 32, 169, 20, 27, 205, 12, 249, 56, 99, 141, 241, 226, 216, 250, 161, 28, 212, 189, 19, 201, 185, 152, 8, 155, 53, 2, 17, 0, 0, 0, 16, 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