Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2dfb6ce68235368d5fe35155606923b7c57cba1cff4e06d03e3bfc7a12f637a

Tx prefix hash: b5a98d8225407528bc4191413f97d9ee804c6c74f895a737c7a5fba99997e773
Tx public key: 5ad83879bd1e373cffbea509ddd729b96a62aeada6b8d6e604311c4370047781
Timestamp: 1711407205 Timestamp [UCT]: 2024-03-25 22:53:25 Age [y:d:h:m:s]: 01:229:19:01:05
Block: 986340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422896 RingCT/type: yes/0
Extra: 015ad83879bd1e373cffbea509ddd729b96a62aeada6b8d6e604311c437004778102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26b09d2b5e5e5388ccca8d5de827ac50025de5e76c30f3f1494ac225eaf84c88 0.600000000000 1446569 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": 986350, "vin": [ { "gen": { "height": 986340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26b09d2b5e5e5388ccca8d5de827ac50025de5e76c30f3f1494ac225eaf84c88" } } ], "extra": [ 1, 90, 216, 56, 121, 189, 30, 55, 60, 255, 190, 165, 9, 221, 215, 41, 185, 106, 98, 174, 173, 166, 184, 214, 230, 4, 49, 28, 67, 112, 4, 119, 129, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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