Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6975cf6f246e9b21af62957f1c0a55aae354c83fa41127480587eae81651228

Tx prefix hash: ba2b979c50e041a9cd6af4a5e2f51d6d9b9eabcfe45c9c9406abd2ceab65eb90
Tx public key: 2885a4e643adbec6fa2c11b702d1808494d2d44187372980aedb80e08aaad815
Timestamp: 1729710134 Timestamp [UCT]: 2024-10-23 19:02:14 Age [y:d:h:m:s]: 00:140:16:25:58
Block: 1138025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100352 RingCT/type: yes/0
Extra: 012885a4e643adbec6fa2c11b702d1808494d2d44187372980aedb80e08aaad8150211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41335e3e503f06befbd0a03a00f9f878280c6a867b693b69095dbd5df5d1fa1a 0.600000000000 1621626 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": 1138035, "vin": [ { "gen": { "height": 1138025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41335e3e503f06befbd0a03a00f9f878280c6a867b693b69095dbd5df5d1fa1a" } } ], "extra": [ 1, 40, 133, 164, 230, 67, 173, 190, 198, 250, 44, 17, 183, 2, 209, 128, 132, 148, 210, 212, 65, 135, 55, 41, 128, 174, 219, 128, 224, 138, 170, 216, 21, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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