Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2cf6a1b212166980c83a607d770efa8473fc51e9f399f76f3a6042ee745312

Tx prefix hash: d1b65dae815561778b4a20cbd7e3fd9a771b4989580bb300000937979fd8f59b
Tx public key: a465d81a193f2f4f164625fd1f41abbb64ad115b56d94e56fa360406ddf3aa2c
Timestamp: 1728620746 Timestamp [UCT]: 2024-10-11 04:25:46 Age [y:d:h:m:s]: 01:040:03:35:43
Block: 1129023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287084 RingCT/type: yes/0
Extra: 01a465d81a193f2f4f164625fd1f41abbb64ad115b56d94e56fa360406ddf3aa2c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faa49a187788ec3e4e5f3401d14b27024e0cbe16eb8c46c59961d1fa7a5d0fdf 0.600000000000 1611846 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": 1129033, "vin": [ { "gen": { "height": 1129023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faa49a187788ec3e4e5f3401d14b27024e0cbe16eb8c46c59961d1fa7a5d0fdf" } } ], "extra": [ 1, 164, 101, 216, 26, 25, 63, 47, 79, 22, 70, 37, 253, 31, 65, 171, 187, 100, 173, 17, 91, 86, 217, 78, 86, 250, 54, 4, 6, 221, 243, 170, 44, 2, 17, 0, 0, 0, 4, 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