Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907a9f8591f83a3778760be68a78aa7c497ad1a4dbc59e363f54686d3e9ce559

Tx prefix hash: cf1973b44cd2d68bd66a8329b92d51b61ca85c8dcdc961bf7648cd0a3f957868
Tx public key: e0e9229f28366ac28c2794c88b03ab07dd2e1ba8e90f1692b20e1e0ff2d16438
Timestamp: 1725144701 Timestamp [UCT]: 2024-08-31 22:51:41 Age [y:d:h:m:s]: 00:291:20:37:30
Block: 1100202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208372 RingCT/type: yes/0
Extra: 01e0e9229f28366ac28c2794c88b03ab07dd2e1ba8e90f1692b20e1e0ff2d16438021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eddad381ac620c505428c3ed6afeb2dc78d4a43fc46a1e6e0868e4d5603b02ba 0.600000000000 1576175 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": 1100212, "vin": [ { "gen": { "height": 1100202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eddad381ac620c505428c3ed6afeb2dc78d4a43fc46a1e6e0868e4d5603b02ba" } } ], "extra": [ 1, 224, 233, 34, 159, 40, 54, 106, 194, 140, 39, 148, 200, 139, 3, 171, 7, 221, 46, 27, 168, 233, 15, 22, 146, 178, 14, 30, 15, 242, 209, 100, 56, 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