Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbf4db6248e06d10743bbe7cdf6ec3c92b2ba77b61643ee8d211c4a7b5bb2ab

Tx prefix hash: 4095303380b4b28dc63666080bd47398c3577899abd2bb288a9f7426839814aa
Tx public key: 0b25094d3680fd7751dd48e59e8cc1609fe4309e1c9411f9173e395a9af1e227
Timestamp: 1578222016 Timestamp [UCT]: 2020-01-05 11:00:16 Age [y:d:h:m:s]: 04:306:03:51:12
Block: 39121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108028 RingCT/type: yes/0
Extra: 010b25094d3680fd7751dd48e59e8cc1609fe4309e1c9411f9173e395a9af1e2270211000000068a2ee0d9000000000000000000

1 output(s) for total of 455.392808401000 dcy

stealth address amount amount idx
00: 5669aa41b67acb6cb42e47112e76ad98c8f87573fb88c23ca926d9b21137f59f 455.392808401000 67221 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": 39131, "vin": [ { "gen": { "height": 39121 } } ], "vout": [ { "amount": 455392808401, "target": { "key": "5669aa41b67acb6cb42e47112e76ad98c8f87573fb88c23ca926d9b21137f59f" } } ], "extra": [ 1, 11, 37, 9, 77, 54, 128, 253, 119, 81, 221, 72, 229, 158, 140, 193, 96, 159, 228, 48, 158, 28, 148, 17, 249, 23, 62, 57, 90, 154, 241, 226, 39, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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