Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49001085e0558cd4787cd86c51fe3d1b2a92036dbe3efafd2e4b7a4758e2865

Tx prefix hash: b2fa337936ca6a58a166b391e68418e60ed0e58ea9141cfd4fbf6977d9fa1f4e
Tx public key: a8ef6972f8394dff7a82595a2fd6ff060d59d3403047739e44656f7781ae92f5
Timestamp: 1733282847 Timestamp [UCT]: 2024-12-04 03:27:27 Age [y:d:h:m:s]: 00:101:02:37:13
Block: 1167576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72066 RingCT/type: yes/0
Extra: 01a8ef6972f8394dff7a82595a2fd6ff060d59d3403047739e44656f7781ae92f50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 205ccc7c0cbbd03424ee2190ac1c519d2fda1dc97cafb4774d3630a86c9edad3 0.600000000000 1653273 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": 1167586, "vin": [ { "gen": { "height": 1167576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "205ccc7c0cbbd03424ee2190ac1c519d2fda1dc97cafb4774d3630a86c9edad3" } } ], "extra": [ 1, 168, 239, 105, 114, 248, 57, 77, 255, 122, 130, 89, 90, 47, 214, 255, 6, 13, 89, 211, 64, 48, 71, 115, 158, 68, 101, 111, 119, 129, 174, 146, 245, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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