Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6e4f7e5be7ccc3afc3e3aa2c5a455b4fbf721965cc8a59cf484c3118632069

Tx prefix hash: de1f5e22e58c583095ef3e7c6761574579f906da74694ec92fbee53761678eb4
Tx public key: cbae42690c534a94230a8ab7f9daeef9f0ceabfdb13ee7a2f242915f5947ccf5
Timestamp: 1723308436 Timestamp [UCT]: 2024-08-10 16:47:16 Age [y:d:h:m:s]: 00:239:05:36:37
Block: 1084988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170847 RingCT/type: yes/0
Extra: 01cbae42690c534a94230a8ab7f9daeef9f0ceabfdb13ee7a2f242915f5947ccf5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b5894702be09e1894ffbef2d4735e7f336c8db28a6095c3a882d6e59bd65e72 0.600000000000 1559457 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": 1084998, "vin": [ { "gen": { "height": 1084988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5894702be09e1894ffbef2d4735e7f336c8db28a6095c3a882d6e59bd65e72" } } ], "extra": [ 1, 203, 174, 66, 105, 12, 83, 74, 148, 35, 10, 138, 183, 249, 218, 238, 249, 240, 206, 171, 253, 177, 62, 231, 162, 242, 66, 145, 95, 89, 71, 204, 245, 2, 17, 0, 0, 0, 5, 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