Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0cedfc32a3e18ae2d1fbd4b374e44edcbc42dbe2799fa499280dc2dfc556d83

Tx prefix hash: 1861cf3c926cfcf81ce0e9b89bbdc57aaee87d40392297a67ef64cee7a8cf106
Tx public key: e28faa6c818b7f34aa3fea3d1163fc569a406b01dce540c4b17efeeb1a74472a
Timestamp: 1713059339 Timestamp [UCT]: 2024-04-14 01:48:59 Age [y:d:h:m:s]: 00:338:01:55:58
Block: 999999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241714 RingCT/type: yes/0
Extra: 01e28faa6c818b7f34aa3fea3d1163fc569a406b01dce540c4b17efeeb1a74472a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 055da09f1a7096a104c96e6de1f0105c5ad5d3cd401d5fc5a471980b50e9a83f 0.600000000000 1460487 of 15

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": 1000009, "vin": [ { "gen": { "height": 999999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "055da09f1a7096a104c96e6de1f0105c5ad5d3cd401d5fc5a471980b50e9a83f" } } ], "extra": [ 1, 226, 143, 170, 108, 129, 139, 127, 52, 170, 63, 234, 61, 17, 99, 252, 86, 154, 64, 107, 1, 220, 229, 64, 196, 177, 126, 254, 235, 26, 116, 71, 42, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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