Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac4c2348641148c47a64ee3a1a7d9859f150620d1119b07d833ffc5115d7b2e

Tx prefix hash: 3da9e08794c64b34cc3453783f760fcee31f1dbdd58fb7e7e05e93f4eb0a3a46
Tx public key: 296f3203a37bd65fdb66403147bf096b5d6dbb76ab78548f6db2eb65ceebed1d
Timestamp: 1696889579 Timestamp [UCT]: 2023-10-09 22:12:59 Age [y:d:h:m:s]: 01:141:00:50:09
Block: 866162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361800 RingCT/type: yes/0
Extra: 01296f3203a37bd65fdb66403147bf096b5d6dbb76ab78548f6db2eb65ceebed1d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.828029417000 dcy

stealth address amount amount idx
00: 1eeea2600d4a270705e97a24a77ade7b92d4b64e55fdce4d2cfdc925f6317364 0.828029417000 1320734 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": 866172, "vin": [ { "gen": { "height": 866162 } } ], "vout": [ { "amount": 828029417, "target": { "key": "1eeea2600d4a270705e97a24a77ade7b92d4b64e55fdce4d2cfdc925f6317364" } } ], "extra": [ 1, 41, 111, 50, 3, 163, 123, 214, 95, 219, 102, 64, 49, 71, 191, 9, 107, 93, 109, 187, 118, 171, 120, 84, 143, 109, 178, 235, 101, 206, 235, 237, 29, 2, 17, 0, 0, 0, 1, 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