Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d9661332cb7ce8003a40de20be8950f309a98148c15b64310894cceebc310b

Tx prefix hash: 2df40f83eb519e00dc69b477ed9b571f47f57f0d62a78768f6ab23eeb63981af
Tx public key: 551423d6e4ce0d02de5091b469c5ae4b9e29910ec16c0bfdb9399bde7f62a967
Timestamp: 1724899979 Timestamp [UCT]: 2024-08-29 02:52:59 Age [y:d:h:m:s]: 00:224:03:54:10
Block: 1098171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160079 RingCT/type: yes/0
Extra: 01551423d6e4ce0d02de5091b469c5ae4b9e29910ec16c0bfdb9399bde7f62a967021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9113d6ab2f7b5f040f8ab80e05eb07c56ed3b0d6d9b403930298469abc2e4dd6 0.600000000000 1573798 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": 1098181, "vin": [ { "gen": { "height": 1098171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9113d6ab2f7b5f040f8ab80e05eb07c56ed3b0d6d9b403930298469abc2e4dd6" } } ], "extra": [ 1, 85, 20, 35, 214, 228, 206, 13, 2, 222, 80, 145, 180, 105, 197, 174, 75, 158, 41, 145, 14, 193, 108, 11, 253, 185, 57, 155, 222, 127, 98, 169, 103, 2, 17, 0, 0, 0, 3, 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