Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 717a2cddcebf738d909ddb96ecbfef4e42f9bbac964fbc2683f8a82d86f0aee4

Tx prefix hash: 26dda9a8e1a316c5ba4f405cb102367f0a65443c4819b4e3a48d344f726a2ce3
Tx public key: 24b6cf119ef554e9b06b7df9bdad072541882a46d1841667e83c0efbeba2b09f
Timestamp: 1727272887 Timestamp [UCT]: 2024-09-25 14:01:27 Age [y:d:h:m:s]: 00:264:20:55:57
Block: 1117856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189048 RingCT/type: yes/0
Extra: 0124b6cf119ef554e9b06b7df9bdad072541882a46d1841667e83c0efbeba2b09f02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a35686f7997270648e60f5fada7b9bbc79e604918e2cc4b3fb02fe9f2cf9c5bc 0.600000000000 1598839 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": 1117866, "vin": [ { "gen": { "height": 1117856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a35686f7997270648e60f5fada7b9bbc79e604918e2cc4b3fb02fe9f2cf9c5bc" } } ], "extra": [ 1, 36, 182, 207, 17, 158, 245, 84, 233, 176, 107, 125, 249, 189, 173, 7, 37, 65, 136, 42, 70, 209, 132, 22, 103, 232, 60, 14, 251, 235, 162, 176, 159, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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