Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9536ac602cea291079cd66bb00713691d33cd3b50f4c470063ac92df9c818cfb

Tx prefix hash: 149494f55d0d51d6e3ef4109bbbe05fc6b51467f5bc254773a599c0c3ebd6e9a
Tx public key: 2fdd4c938bc5a5c3d5a416754783333f2b4f9b565ca66946b0f8724f0f6db4bd
Timestamp: 1707841914 Timestamp [UCT]: 2024-02-13 16:31:54 Age [y:d:h:m:s]: 01:237:15:59:21
Block: 956754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428568 RingCT/type: yes/0
Extra: 012fdd4c938bc5a5c3d5a416754783333f2b4f9b565ca66946b0f8724f0f6db4bd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51114eb69cd0782ef4df5f42a43081c35af367e072ee206a7dcd5fc97573b8f7 0.600000000000 1416064 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": 956764, "vin": [ { "gen": { "height": 956754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51114eb69cd0782ef4df5f42a43081c35af367e072ee206a7dcd5fc97573b8f7" } } ], "extra": [ 1, 47, 221, 76, 147, 139, 197, 165, 195, 213, 164, 22, 117, 71, 131, 51, 63, 43, 79, 155, 86, 92, 166, 105, 70, 176, 248, 114, 79, 15, 109, 180, 189, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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