Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ca8b60fb3eaab27ee26718375c592ce86d9f4187bc331cb2160dc4582a2b9e7

Tx prefix hash: f14911fd6e58d87a061a7b3ef92bd37291e6b96c68187de3af80741e60cabc41
Tx public key: e61d8d701c609d6b9897f47110bbe87abebe0e72d5ce83261f1fc9a0a17e687a
Timestamp: 1726400155 Timestamp [UCT]: 2024-09-15 11:35:55 Age [y:d:h:m:s]: 00:206:16:01:55
Block: 1110616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147540 RingCT/type: yes/0
Extra: 01e61d8d701c609d6b9897f47110bbe87abebe0e72d5ce83261f1fc9a0a17e687a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe5ae50a6c2e64c7b5d748c672ab31ee2745cf55028b1f7847cafe5fb9c6b028 0.600000000000 1589283 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": 1110626, "vin": [ { "gen": { "height": 1110616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe5ae50a6c2e64c7b5d748c672ab31ee2745cf55028b1f7847cafe5fb9c6b028" } } ], "extra": [ 1, 230, 29, 141, 112, 28, 96, 157, 107, 152, 151, 244, 113, 16, 187, 232, 122, 190, 190, 14, 114, 213, 206, 131, 38, 31, 31, 201, 160, 161, 126, 104, 122, 2, 17, 0, 0, 0, 3, 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