Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0aecf3feb47d3271ec84de3a9ac928f6b27129781ec9d3f66b8b9491a260c4

Tx prefix hash: 1a9f8d57983f2e43f31f2ac44b472478a1830157e46284e0fd516bc3c0516807
Tx public key: 928359b45483c16516e555aa2d66d61f598a64abdff0b214aa0ec390e2e71d8a
Timestamp: 1720374517 Timestamp [UCT]: 2024-07-07 17:48:37 Age [y:d:h:m:s]: 00:268:10:21:49
Block: 1060653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191779 RingCT/type: yes/0
Extra: 01928359b45483c16516e555aa2d66d61f598a64abdff0b214aa0ec390e2e71d8a0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1fb8c772110ab389c0ba38d248ed077f5a1b428815a41301883620513e1f007 0.600000000000 1531138 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": 1060663, "vin": [ { "gen": { "height": 1060653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1fb8c772110ab389c0ba38d248ed077f5a1b428815a41301883620513e1f007" } } ], "extra": [ 1, 146, 131, 89, 180, 84, 131, 193, 101, 22, 229, 85, 170, 45, 102, 214, 31, 89, 138, 100, 171, 223, 240, 178, 20, 170, 14, 195, 144, 226, 231, 29, 138, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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