Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bae6ff6fc2cd0078a7e8b4f5388ce9008b72965bc6e94751db64e1c9fb038af

Tx prefix hash: cbf0b8c1ffd32ef799c451708a9da107f97a9f95fd4cf73db31d381d403762ab
Tx public key: fbe639b9910f81715d8c90a13076f2f5a8624d147da507af646a6a721e743e46
Timestamp: 1741135850 Timestamp [UCT]: 2025-03-05 00:50:50 Age [y:d:h:m:s]: 00:306:18:01:25
Block: 1232319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217069 RingCT/type: yes/0
Extra: 01fbe639b9910f81715d8c90a13076f2f5a8624d147da507af646a6a721e743e460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4918c35ab8e68272524826d16a5d9ee8d9b97727b2b631acfa51862c6b4295f 0.600000000000 1719232 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": 1232329, "vin": [ { "gen": { "height": 1232319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4918c35ab8e68272524826d16a5d9ee8d9b97727b2b631acfa51862c6b4295f" } } ], "extra": [ 1, 251, 230, 57, 185, 145, 15, 129, 113, 93, 140, 144, 161, 48, 118, 242, 245, 168, 98, 77, 20, 125, 165, 7, 175, 100, 106, 106, 114, 30, 116, 62, 70, 2, 17, 0, 0, 0, 2, 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