Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391e0b55053a4a7224c51ff6b09d73f3fa354ae9a2b4fa5e19ac7b2da4afbd28

Tx prefix hash: 7c16747760d40788fbe20e76e2182b00105e98f057d5e436c030b2971ffc15ac
Tx public key: c0afb4ec0f1a9f66125ca39182c93cb929b8fb8a0b9cbca116311bf267d82628
Timestamp: 1727147197 Timestamp [UCT]: 2024-09-24 03:06:37 Age [y:d:h:m:s]: 00:266:16:09:06
Block: 1116810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190339 RingCT/type: yes/0
Extra: 01c0afb4ec0f1a9f66125ca39182c93cb929b8fb8a0b9cbca116311bf267d82628021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a628e6c1e9c2e750f26c4e59d74419ff914a59616fcdde9ca40cbe2d66a5a3cb 0.600000000000 1597425 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": 1116820, "vin": [ { "gen": { "height": 1116810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a628e6c1e9c2e750f26c4e59d74419ff914a59616fcdde9ca40cbe2d66a5a3cb" } } ], "extra": [ 1, 192, 175, 180, 236, 15, 26, 159, 102, 18, 92, 163, 145, 130, 201, 60, 185, 41, 184, 251, 138, 11, 156, 188, 161, 22, 49, 27, 242, 103, 216, 38, 40, 2, 17, 0, 0, 0, 5, 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