Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3185190596742b9d33b4e5105e973ac80fcc929a8875b0aa029d43fca1e72f5

Tx prefix hash: c180cb2e1b1b9d71baa6cc09cfd4aeec7d60953aa314b4cb13c4f18752113869
Tx public key: 99f2f8e1b8f56a3dccc9f2cb9216ef35a734a6864a8bee314088cf1e045155a1
Timestamp: 1721999551 Timestamp [UCT]: 2024-07-26 13:12:31 Age [y:d:h:m:s]: 01:104:06:12:46
Block: 1074135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333002 RingCT/type: yes/0
Extra: 0199f2f8e1b8f56a3dccc9f2cb9216ef35a734a6864a8bee314088cf1e045155a1021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2175c5aeac0b98d8b22549344ce3c09a65a31e19f6ad1b52e7910b8308e380f6 0.600000000000 1546648 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": 1074145, "vin": [ { "gen": { "height": 1074135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2175c5aeac0b98d8b22549344ce3c09a65a31e19f6ad1b52e7910b8308e380f6" } } ], "extra": [ 1, 153, 242, 248, 225, 184, 245, 106, 61, 204, 201, 242, 203, 146, 22, 239, 53, 167, 52, 166, 134, 74, 139, 238, 49, 64, 136, 207, 30, 4, 81, 85, 161, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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