Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f249f6de4763ad047d3e541e5cf8d842f198f32ba7394ac62627f810aab42145

Tx prefix hash: fe41cef5cac54f2b700e3bacf1eddd7804fba13d6e66b8151e7a2bb8635a77c0
Tx public key: 11a06cca2b1252cde06f25cdd220012b61cc44d26eaf823cef2d8aa5fe1b09ef
Timestamp: 1698489808 Timestamp [UCT]: 2023-10-28 10:43:28 Age [y:d:h:m:s]: 01:193:05:47:30
Block: 879449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399105 RingCT/type: yes/0
Extra: 0111a06cca2b1252cde06f25cdd220012b61cc44d26eaf823cef2d8aa5fe1b09ef02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.748204645000 dcy

stealth address amount amount idx
00: c76eeee726a09b53ad3a5655d1b5ae6b0e5aedd7e7f0d3ac032aa35c042fe284 0.748204645000 1334971 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": 879459, "vin": [ { "gen": { "height": 879449 } } ], "vout": [ { "amount": 748204645, "target": { "key": "c76eeee726a09b53ad3a5655d1b5ae6b0e5aedd7e7f0d3ac032aa35c042fe284" } } ], "extra": [ 1, 17, 160, 108, 202, 43, 18, 82, 205, 224, 111, 37, 205, 210, 32, 1, 43, 97, 204, 68, 210, 110, 175, 130, 60, 239, 45, 138, 165, 254, 27, 9, 239, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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